docs: clarify pnpm runtime management conflicts - #2620
Merged
fengmk2 merged 2 commits intoSep 7, 2026
Merged
Conversation
✅ Deploy Preview for viteplus-preview canceled.
|
liangmiQwQ
marked this pull request as ready for review
September 6, 2026 21:57
fengmk2
approved these changes
Sep 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vite+ and pnpm can both manage Node.js, leading to duplicate downloads and inconsistent runtime versions between commands.
This PR adds a VitePress tip to the Environment guide documenting
pnpm config set --global runtimeOnFail ignorefor pnpm 11+. It explains that the global setting also disables pnpm's automatic management of other declared runtimes, including Bun and Deno, so users can consider the impact on their projects before applying it.🤖 Generated with Codex